Skocz do zawartości


Zdjęcie

[POMOCY] bsod memory corruption? windows 7 nowy komp


  • Zaloguj się, aby dodać odpowiedź
3 odpowiedzi w tym temacie

#1 kleyou

kleyou

    Nowy

  • 2 postów

Napisano 05 08 2013 - 13:16

Witam. Proszę uprzejmię o pomoc, bo już wyczerpały mi się pomysły. Komp złożony przeze mnie, od początku był problem a to z bootowaniem z usb, a również z instalacją windowsa (pomogło wyjęcie jednej kości pamięci i przełożenie jej na inny slot). Mimo wszystko co jakiś czas wyskakuje blue screen, system zamula i wolno się włącza.

Windows memory diagnostic wywala błąd hardware. Jeszcze nie testowałem pamiątek memtestem - zrobię to dzisiaj.

SPRZĘT:

asrock p67 pro3

i5 3570k

HD 7950 gigabyte rev 1.0

ram patriot intel masters PVI38G160C9K   2x4GB 1600mhz

seagate barracuda 500gb ST500DM002

CORSAIR VS 550

==================================================================

Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\080513-19687-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800`02e02000 PsLoadedModuleList = 0xfffff800`0303ee70
Debug session time: Mon Aug  5 01:38:02.521 2013 (GMT+2)
System Uptime: 0 days 0:06:14.473
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6837f75fb80, 0, fffff80002e45c07, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+11b )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff6837f75fb80, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002e45c07, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030a90e0
 fffff6837f75fb80

FAULTING_IP:
nt!MiDeleteAddressesInWorkingSet+11b
fffff800`02e45c07 488b1e          mov     rbx,qword ptr [rsi]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  mscorsvw.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009621010 -- (.trap 0xfffff88009621010)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000098000000000 rbx=0000000000000000 rcx=0000000000000c45
rdx=0000000000000010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e45c07 rsp=fffff880096211a0 rbp=fffff70001083598
 r8=fffffa8006f34cc8  r9=0000000000000001 r10=00000000000001b6
r11=fffff70001080000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!MiDeleteAddressesInWorkingSet+0x11b:
fffff800`02e45c07 488b1e          mov     rbx,qword ptr [rsi] ds:0572:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ef0041 to fffff80002e71880

STACK_TEXT:  
fffff880`09620ea8 fffff800`02ef0041 : 00000000`00000050 fffff683`7f75fb80 00000000`00000000 fffff880`09621010 : nt!KeBugCheckEx
fffff880`09620eb0 fffff800`02e6f96e : 00000000`00000000 0000000f`ffffffff 00000000`00001000 fffff800`02fa5bfe : nt! ?? ::FNODOBFM::`string'+0x4040b
fffff880`09621010 fffff800`02e45c07 : 00000003`00000000 62100001`84bcf025 fffff700`01083590 fffff683`ff75c1e8 : nt!KiPageFault+0x16e
fffff880`096211a0 fffff800`02e44856 : fffffa80`06f34930 fffffa80`00000010 fffff8a0`000001b6 00000000`00000000 : nt!MiDeleteAddressesInWorkingSet+0x11b
fffff880`09621a50 fffff800`0315109b : fffff8a0`0900bc50 00000000`00000001 00000000`00000000 fffffa80`0a6b1b60 : nt!MmCleanProcessAddressSpace+0x96
fffff880`09621aa0 fffff800`0312a1fb : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`09621b60 fffff800`02e70ad3 : fffffa80`06f34930 000007fe`00000000 00000000`002d4101 fffffa80`0a6b1b60 : nt!NtTerminateProcess+0x25b
fffff880`09621be0 00000000`77cbf97a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0017f578 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cbf97a


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!MiDeleteAddressesInWorkingSet+11b
fffff800`02e45c07 488b1e          mov     rbx,qword ptr [rsi]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiDeleteAddressesInWorkingSet+11b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5147dc36

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiDeleteAddressesInWorkingSet+11b

BUCKET_ID:  X64_0x50_nt!MiDeleteAddressesInWorkingSet+11b

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff6837f75fb80, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002e45c07, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS:  fffff6837f75fb80

FAULTING_IP:
nt!MiDeleteAddressesInWorkingSet+11b
fffff800`02e45c07 488b1e          mov     rbx,qword ptr [rsi]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  mscorsvw.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009621010 -- (.trap 0xfffff88009621010)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000098000000000 rbx=0000000000000000 rcx=0000000000000c45
rdx=0000000000000010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e45c07 rsp=fffff880096211a0 rbp=fffff70001083598
 r8=fffffa8006f34cc8  r9=0000000000000001 r10=00000000000001b6
r11=fffff70001080000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!MiDeleteAddressesInWorkingSet+0x11b:
fffff800`02e45c07 488b1e          mov     rbx,qword ptr [rsi] ds:0572:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ef0041 to fffff80002e71880

STACK_TEXT:  
fffff880`09620ea8 fffff800`02ef0041 : 00000000`00000050 fffff683`7f75fb80 00000000`00000000 fffff880`09621010 : nt!KeBugCheckEx
fffff880`09620eb0 fffff800`02e6f96e : 00000000`00000000 0000000f`ffffffff 00000000`00001000 fffff800`02fa5bfe : nt! ?? ::FNODOBFM::`string'+0x4040b
fffff880`09621010 fffff800`02e45c07 : 00000003`00000000 62100001`84bcf025 fffff700`01083590 fffff683`ff75c1e8 : nt!KiPageFault+0x16e
fffff880`096211a0 fffff800`02e44856 : fffffa80`06f34930 fffffa80`00000010 fffff8a0`000001b6 00000000`00000000 : nt!MiDeleteAddressesInWorkingSet+0x11b
fffff880`09621a50 fffff800`0315109b : fffff8a0`0900bc50 00000000`00000001 00000000`00000000 fffffa80`0a6b1b60 : nt!MmCleanProcessAddressSpace+0x96
fffff880`09621aa0 fffff800`0312a1fb : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`09621b60 fffff800`02e70ad3 : fffffa80`06f34930 000007fe`00000000 00000000`002d4101 fffffa80`0a6b1b60 : nt!NtTerminateProcess+0x25b
fffff880`09621be0 00000000`77cbf97a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0017f578 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cbf97a


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!MiDeleteAddressesInWorkingSet+11b
fffff800`02e45c07 488b1e          mov     rbx,qword ptr [rsi]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiDeleteAddressesInWorkingSet+11b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5147dc36

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiDeleteAddressesInWorkingSet+11b

BUCKET_ID:  X64_0x50_nt!MiDeleteAddressesInWorkingSet+11b

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff6837f75fb80, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002e45c07, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS:  fffff6837f75fb80

FAULTING_IP:
nt!MiDeleteAddressesInWorkingSet+11b
fffff800`02e45c07 488b1e          mov     rbx,qword ptr [rsi]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  mscorsvw.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009621010 -- (.trap 0xfffff88009621010)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000098000000000 rbx=0000000000000000 rcx=0000000000000c45
rdx=0000000000000010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e45c07 rsp=fffff880096211a0 rbp=fffff70001083598
 r8=fffffa8006f34cc8  r9=0000000000000001 r10=00000000000001b6
r11=fffff70001080000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!MiDeleteAddressesInWorkingSet+0x11b:
fffff800`02e45c07 488b1e          mov     rbx,qword ptr [rsi] ds:0572:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ef0041 to fffff80002e71880

STACK_TEXT:  
fffff880`09620ea8 fffff800`02ef0041 : 00000000`00000050 fffff683`7f75fb80 00000000`00000000 fffff880`09621010 : nt!KeBugCheckEx
fffff880`09620eb0 fffff800`02e6f96e : 00000000`00000000 0000000f`ffffffff 00000000`00001000 fffff800`02fa5bfe : nt! ?? ::FNODOBFM::`string'+0x4040b
fffff880`09621010 fffff800`02e45c07 : 00000003`00000000 62100001`84bcf025 fffff700`01083590 fffff683`ff75c1e8 : nt!KiPageFault+0x16e
fffff880`096211a0 fffff800`02e44856 : fffffa80`06f34930 fffffa80`00000010 fffff8a0`000001b6 00000000`00000000 : nt!MiDeleteAddressesInWorkingSet+0x11b
fffff880`09621a50 fffff800`0315109b : fffff8a0`0900bc50 00000000`00000001 00000000`00000000 fffffa80`0a6b1b60 : nt!MmCleanProcessAddressSpace+0x96
fffff880`09621aa0 fffff800`0312a1fb : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`09621b60 fffff800`02e70ad3 : fffffa80`06f34930 000007fe`00000000 00000000`002d4101 fffffa80`0a6b1b60 : nt!NtTerminateProcess+0x25b
fffff880`09621be0 00000000`77cbf97a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0017f578 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cbf97a


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!MiDeleteAddressesInWorkingSet+11b
fffff800`02e45c07 488b1e          mov     rbx,qword ptr [rsi]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiDeleteAddressesInWorkingSet+11b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5147dc36

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiDeleteAddressesInWorkingSet+11b

BUCKET_ID:  X64_0x50_nt!MiDeleteAddressesInWorkingSet+11b

Followup: MachineOwner
---------

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7600.2.0.0.256.1
  Locale ID:    1045

Additional information about the problem:
  BCCode:    124
  BCP1:    0000000000000000
  BCP2:    FFFFFA800623D028
  BCP3:    00000000B2000000
  BCP4:    0000000081000402
  OS Version:    6_1_7600
  Service Pack:    0_0
  Product:    256_1

Files that help describe the problem:
  C:\Windows\Minidump\080513-12823-01.dmp
  C:\Users\kleyou\AppData\Local\Temp\WER-25568-0.sysdata.xml

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7600.2.0.0.256.1
  Locale ID:    1045

Additional information about the problem:
  BCCode:    50
  BCP1:    FFFFF6837F75FB80
  BCP2:    0000000000000000
  BCP3:    FFFFF80002E45C07
  BCP4:    0000000000000005
  OS Version:    6_1_7600
  Service Pack:    0_0
  Product:    256_1

Files that help describe the problem:
  C:\Windows\Minidump\080513-19687-01.dmp
  C:\Users\kleyou\AppData\Local\Temp\WER-111852-0.sysdata.xml

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Proszę każdego kto ma jakieś pomysły, o pomoc. Jestem bezradny :(

 

 



  • 0

#2 makensis

makensis

    Naczelny

  • 5 036 postów

Napisano 05 08 2013 - 14:11

Nowy komp? Mi to wygląda na procesor nie stykający na całej powierzchni z gniazdem procesora. To najczęstsza przyczyna po pomyłkach z odpowiednim umieszczeniem pamięci w slotach(kanał Dual Channel to zazwyczaj niebieski slot). Rozkręć kompa, ostrożnie wyjmij procesor, sprawdź czy żadna z nóżek gniazda nie jest zagięta oraz powierzchnia styku procesora zabrudzona i włóż ponownie.



  • 0

#3 kleyou

kleyou

    Nowy

  • 2 postów

Napisano 06 08 2013 - 01:02

Nowy komp? Mi to wygląda na procesor nie stykający na całej powierzchni z gniazdem procesora. To najczęstsza przyczyna po pomyłkach z odpowiednim umieszczeniem pamięci w slotach(kanał Dual Channel to zazwyczaj niebieski slot). Rozkręć kompa, ostrożnie wyjmij procesor, sprawdź czy żadna z nóżek gniazda nie jest zagięta oraz powierzchnia styku procesora zabrudzona i włóż ponownie.

 

Zrobiłem wg wskazówek - nie pomogło. Piny na sockecie i procku wyglądają na proste, są czyste.

 

 

Po przetestowaniu memtestem wygląda na to, że jedna z kości jest zrypana (jakieś 99%) błędów, na drugiej kości 0.

 

Jakieś sugestie?


  • 0

#4 bipiw

bipiw

    Zaawansowany użytkownik

  • 1 180 postów

Napisano 06 08 2013 - 10:34

Jeśli przed testem przeczyściłeś styki kości i przedmuchałeś sloty sprężonym powietrzem to sugestia może być tylko jedna. Wymiana kości.



  • 0




Użytkownicy przeglądający ten temat: 0

0 użytkowników, 0 gości, 0 anonimowych